↓Skip to main content
0
  1. Wiki/

Email Encyclopedia: What is MIME

Table of Contents

Alibaba Mail More Products and Services

MIME (Multipurpose Internet Mail Extensions) is an internet standard used to extend email systems to support non-ASCII character sets, multimedia attachments, and other non-text content. MIME allows email to go beyond plain text transmission, enabling the transfer of images, audio, video, application files, and various other types of data.

Background and Development #

Email was initially designed based on SMTP (Simple Mail Transfer Protocol), which could only transmit ASCII characters, i.e., English text. However, as the internet evolved, user demands for email functionality increased, especially in international communication and multimedia transmission. The MIME standard was developed to meet these needs.

MIME was first proposed by Nathaniel Borenstein and others in 1991 and was initially defined in RFC 1341. Subsequently, the MIME standard was further refined in RFC 2045 through RFC 2049. Currently, MIME has become one of the core standards for email systems and is also widely used in other protocols such as HTTP and SIP.

Main Functions of MIME #

The main goals of MIME are to extend email functionality to support:

  1. Non-ASCII character sets: Such as Chinese, Japanese, Korean, and other multilingual texts.
  2. Multimedia attachments: Such as images, audio, video, and other non-text files.
  3. Multi-part message structure: Allowing a single email to contain multiple different types of attachments or content sections.
  4. Content encoding: Ensuring binary data can be transmitted through email systems that only support ASCII.

MIME Structure #

MIME messages consist of a header and content, where the header contains MIME-related metadata, and the content contains the actual data. MIME defines multiple header fields, common ones include:

  • MIME-Version: Specifies the MIME version used, typically 1.0.
  • Content-Type: Indicates the type and format of the content.
  • Content-Transfer-Encoding: Describes the encoding method used for the content.
  • Content-Disposition: Indicates whether the content should be displayed inline or downloaded as an attachment.
  • Content-ID and Content-Location: Used to identify unique identifiers or locations of content.

MIME Header Example #

MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="frontier"

This is a multi-part message in MIME format.

--frontier
Content-Type: text/plain

This is the message body.

--frontier
Content-Type: image/jpeg
Content-Transfer-Encoding: base64

...base64 encoded image data...

--frontier--

In this example, the email contains a text part and a JPEG image attachment, encapsulated using the multipart/mixed type.

Content-Type: Content Type #

The Content-Type field is used to specify the type of email content, consisting of a main type and a subtype, formatted as type/subtype. Common types include:

  • text/plain: Plain text.
  • text/html: HTML formatted text.
  • image/jpeg: JPEG image.
  • audio/mpeg: MPEG audio.
  • video/mp4: MP4 video.
  • application/pdf: PDF document.
  • multipart/mixed: Mixed content, used to contain multiple parts.
  • multipart/alternative: Alternative content, for example, containing both plain text and HTML versions of the email body.
  • multipart/related: Related content, such as images embedded in HTML emails.
  • message/rfc822: Nested email.

Content-Transfer-Encoding: Transfer Encoding #

Since early email systems only supported ASCII characters, non-ASCII content needed to be encoded for transmission. MIME defines the following common encoding methods:

  • 7bit: Default encoding, suitable for ASCII characters.
  • 8bit: Supports 8-bit characters but depends on email server support.
  • quoted-printable: Used to encode content containing a small number of non-ASCII characters, such as Chinese email body text.
  • base64: Encodes binary data as ASCII characters, suitable for attachments and other non-text content.
  • binary: Directly uses binary data but is less commonly used.

Multipart Messages #

MIME allows an email to contain multiple parts, each with different content types and encoding methods. This structure is implemented through the multipart/* type, with common types including:

  • multipart/mixed: Used to contain multiple different types of content, typically used for email attachments.
  • multipart/alternative: Used to provide different representations of the same content, such as providing both plain text and HTML versions.
  • multipart/related: Used to contain interrelated content, such as images embedded in HTML emails.
  • multipart/signed and multipart/encrypted: Used to support email signatures and encryption.

MIME and Modern Email Systems #

MIME has become one of the foundational standards of modern email systems. Almost all modern email clients (such as Outlook, Gmail, Apple Mail, etc.) and servers support the MIME standard. Additionally, MIME is widely applied in web protocols; for example, the HTTP protocol uses MIME types to identify the types of web resources (such as text/html, application/javascript, etc.).

MIME and Security #

MIME itself does not provide security features, but it provides a foundation for other security protocols. For example:

  • S/MIME (Secure/Multipurpose Internet Mail Extensions): Adds digital signature and encryption functions based on MIME, used to implement secure email communication.
  • OpenPGP/MIME: Combines the OpenPGP protocol with MIME to provide end-to-end encryption and signature capabilities.

These protocols utilize MIME’s structure to encapsulate encrypted or signed data, thereby achieving the confidentiality and integrity of email content.

Limitations of MIME #

Although MIME greatly expands email functionality, it also has some limitations:

  1. Compatibility issues: Some older email clients or servers may not fully support MIME, causing some content to not display correctly.
  2. Encoding efficiency issues: Encoding methods such as base64 increase data size, affecting transmission efficiency.
  3. Spam abuse: MIME’s attachment mechanism is often used by spam senders to spread malware.

The Future of MIME #

As email technology evolves, the MIME standard continues to evolve as well. For example:

  • UTF-8 support: Standards such as RFC 6532 extend MIME’s support for UTF-8 character sets, making it easier for emails to transmit multilingual content.
  • Internationalized email addresses: The EAI (Email Address Internationalization) standard allows non-ASCII characters to be used as email addresses, further enhancing the internationalization capabilities of email systems.
  • Security enhancements: With the development of email security protocols such as S/MIME, DKIM, SPF, and DMARC, the MIME structure is being used for more secure email communications.

Summary #

MIME is one of the core standards of modern email systems, enabling emails to transmit non-text content such as images, audio, video, PDFs, and more. MIME implements structured and encoded email content by defining fields such as Content-Type and Content-Transfer-Encoding, providing the technical foundation for the multipurpose nature of email. Although MIME has some limitations, its important role in internet communications is irreplaceable and continues to evolve with technological advancements.

Related Entries:

  • Electronic Mail
  • SMTP
  • S/MIME
  • UTF-8
  • HTTP
  • Email Clients
  • Spam
  • Digital Signatures
  • Encrypted Email

References:

  • RFC 2045: Format of Internet Message Bodies
  • RFC 2046: Media Type Specifications and Parameter Definitions
  • RFC 2047: Message Header Extensions for Non-ASCII Text
  • RFC 2048: Multipurpose Internet Mail Extensions (MIME) Parameter Registrations
  • RFC 2049: Conformance Criteria and Examples
  • Wikipedia: MIME
  • IANA: MIME Media Types